Skip to content

Conversation

@tassaron
Copy link
Collaborator

I removed the second scale spinbox from the Image component for reasons I wrote about here, which means I should change the version number since the saved settings are different now. Since I'm doing that anyway, might as well improve the settings to make a bit more sense.

In this pull request the Image component widget is changed to this:
Screenshot_20260121_104941

And selecting a different resize mode disabled the scale spinbox:
Screenshot_20260121_105048

Now as well as scale and stretch, we have a third option "cover" that makes the image fit without distorting its aspect ratio. This seems a bit more useful than the previous options.

I also wrote tests for some toolkit functions, undoing component updates, and some specific methods of 3 components (classic visualizer, image, and title text). While doing this I fixed two incorrect comments and replaced numpy.seterr with a context manager version

I will merge this late tomorrow unless I discover problems with it or someone has objections

previously these tests would fail if they ran before qtbot was initialized by another test. I'm now running tests in a random order
previous commit did most of it but this polishes the GUI - fixes #89
3 resize modes are scale, cover, and stretch. Scale only applies when resizeMode is set to scale. Cover uses ImageOps.fit() to stretch while maintaining aspect ratio. Also, spinBox_scale was moved to be underneath comboBox_resizeMode.
the purpose is to allow easier reuse in other components
this causes the image to scale up and down slightly based on the input audio file
@tassaron
Copy link
Collaborator Author

I added another option to scale the image up and down slightly in response to the input audio file, so you can use the Image component as a visualizer now.

This is a similar effect to some videos I've seen where the creator pulses their avatar in response to the audio.

increases rendering speed of a 1-minute video by 12 seconds (based on two manual tests anyway)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants